Skip to content

fix: report Trivy CI as failed when the scan finds vulnerabilities - #190

Merged
dnlopes merged 1 commit into
mainfrom
fix/trivy-status
Nov 5, 2026
Merged

dnlopes merged 1 commit into
mainfrom
fix/trivy-status

Conversation

@dnlopes

@dnlopes dnlopes commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Fixes the Trivy CI status, which reported success when the scan found vulnerabilities. The scan step uses continue-on-error, so success() stayed true until the last step failed the job, after the status was already posted. The status steps now read the scan outcome.

Trivy CI is a required check, so it can now block merges in repositories with findings.

Verified with actionlint. The fix is tested on Makefiles with a vulnerable dependency after this merges and releases.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions github-actions Bot added patch Backwards-compatible bug fixes size-S Small size changes fix Solves a bug labels Nov 5, 2026
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Trivy Security Scan Results

Note

No vulnerabilities found


Scan performed by Trivy v0.69.3

@dnlopes
dnlopes merged commit 234f5b4 into main Nov 5, 2026
6 checks passed
@dnlopes
dnlopes deleted the fix/trivy-status branch November 5, 2026 00:45
@github-actions

github-actions Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 1.30.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix Solves a bug patch Backwards-compatible bug fixes released Issue already released size-S Small size changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant